Important: Refer to relevant IBM blade center or Cisco UCS C210M2 documentation for system hardware details.|
•
|
Processors: Up to 2 x Dual-core Intel Xeon Processor up to 3.0GHz.
|
|
•
|
Memory: 32GB Fully Buffered DIMM. Minimum: 4GB.
|
|
•
|
Hard drives: 140GB, minimum 40GB.
|
|
•
|
Networking: Dual Gigabit Ethernet up to 8 ports. Minimum - 2 ports for single host installation, 4 ports for cluster installation.
|
|
•
|
Max cache : 4MB L2 shared cache.
|
|
•
|
Front side bus: 1333 MHz.
|
Important: Hardware requirements may vary as per SSC deployment configuration.|
database_HOME
|
Stores home directory path for database.
|
|
|
IMDB_App_HOME
|
Important: Before proceeding with SSC cluster installation you need to define a detailed IP map that co-relates the SSC management and application interfaces as well as primary and standby databases with available IP addresses for entire SSC deployment. During installation you must ensure that eth0 is selected as a management interface.
|
•
|
Traffic VLAN: It carries data traffic for the SSC cluster. Maximum bandwidth should be configured for this VLAN. It serves the Sh, En and SPR API interfaces along with a standby interface for the database.
|
|
•
|
Management VLAN: It carries management traffic for the SSC cluster. This VLAN provides access to the user interface for the deployed SSC cluster along with the access for an interface to Policy Provisioning Tool (PPT). As well as web access to the console that manages IBM/Cisco chassis.
|
|
•
|
Private VLAN: It provides inter-process communication between the application nodes as well as carries the private traffic between the database instances.
|
SSC installation wizard is available in an archived format as ssc_<version>_rhel_x86_qa1.tar. Create a temporary directory where this wizard can be extracted, by issuing following command:
mkdir/tmpinst
During the installation use tail command to view SSC installation logs being created in/var/log/messages file, to verify the success or failure of commands being executed by the SSC installer. After installation refer to the installation summery captured in Subscriber_Services_Controller_InstallLog.log file which is located in /localhome/install folder.
Important: For the cluster installation, the installer executable must be available on all the blades where you want to install the SSC.SSC Installation logs are stored in system logs /var/log/messages file. If there are any failures in system logs then, fix those errors by referring to Troubleshooting chapter, and re-execute the installation steps using Previous and Next buttons, provided by installer GUI.
tar -xvf ssc_<version>_rhel_x86_qa1.tar
|
Step 6
|
SSC Installer displays the Introduction screen.
|
|
Step 7
|
Click Next
|
SSC Installer displays License Agreement screen. Select the option I accept terms of license agreement.
|
Step 8
|
Click Next
|
SSC Installer displays Cluster Installation screen. As this installation is for single host. Select Number of Blades as 1. The Choose Blade field displays the available blade. Using Choose Interface field select the interface for this blade.
|
Step 9
|
Click Add to add this interface
|
|
Step 10
|
Click Next
|
SSC Installer displays Installation Set screen. Select whether this is a primary site or a stand -by site. Select whether you want to install Application, Primary Database or Secondary Database on this blade.
Important: In a multi-host cluster environment, if you are implementing the geo-redundancy, then as per your IP map specify whether you want to use this SSC installation as primary site or as a stand-by site.
Important: Primary and standby databases cannot be configured on same blade.|
Step 11
|
Click Next
|
Installer configures database and IMDB instances. After installing selected Installation Set, SSC installer creates database schema and IMDB cache. Ensure that INSTALL_DB in /localhome/install/ssctmp.properties is set to true, if database schema is to be installed on this blade. database_DB_HOST in /localhome/ssc/install/spr_install/createSSC_grid.cfg is set to the host name of box where primary database instance is created. IMDB_* in /localhome/SSC/install/spr_install/cratessc_grid.cfg is set to the hostnames of the boxes that need to be part of the IMDB grid. InstanceName in /localhome/ssc/etc/system.cfg is set to the database instance that is to be configured on this box.
|
Step 12
|
SSC Installer configures Kernel Parameters, Sets network configuration files, adds users and groups. Time required to configure these parameters depends upon your hardware and the options that you have selected. During this period the Next button will be grayed out. Click Next when that button is available.
|
|
Step 13
|
SSC Installer displays Pre- Installation Summary screen.
|
|
Step 14
|
Click Install.
|
|
Step 15
|
Click Next
|
SSC Installer displays Installation Complete screen, when SSC application is installed on your system. After installation refer to overall summary of installation steps along with success or failure indicators in /localhome/install/Subscriber_Services_Controller_InstallLog.log
Refer to the installation procedure documented in the section Installing SSC on a Single Host. On each host or blade, follow this procedure from step 1 up to the cluster installation step.
|
Step 6
|
Click on Add button to include this blade in the cluster.
|
Refer to step 12,the Cluster Installation step in single host installation section. When the installer prompts for data base and IMDB configuration for this node, ensure that:
|
•
|
ORACLE_DB_HOST in /localhome/ssc/install/spr_install/createSSC_grid.cfg is set to the hostname of box where primary database instance is created.
|
|
•
|
IMDB_DB_* in /localhome/ssc/install/spr_install/createSSC_grid.cfg is set appropriately as per cluster plan
|
|
•
|
InstanceName in /localhome/ssc/etc/system.cfg is set to db instance configured on database box
|
Important: Increment the instance id for every node or blade.
Important: For both Cisco UCS and IBM Blade Center, you need to ensure that the hardware is configured for recovery from eth card failure, before attempting the HA configuration.In a cluster deployment high availability can be configured by setting some parameters values in the file/localhome/install/ssctmp.properties. Ensure that before starting installation of cluster RPMs, the keys RPM-GPG-KEY-redhat-beta and RPM-GPG-KEY-redhat-release are imported.
Important: For a single host SSC deployment, High Availability (HA) is not supported, however failure detection and recovery mechanisms exist for application processes, database, IMDB and network link for such deployment.|
Step 1
|
With root administrative privilege access the file /localhome/install/ssctmp.properties .
|
|
Step 2
|
Enable HA option by setting value of INSTALL_HA_ENABLED parameter to 1.
|
|
Step 3
|
Set Floating point IPs for Sh Management, Event Notification and Profile Controller interfaces by setting values of INSTALL_EXT_PROFILE_INTERFACE,INSTALL_EXT_EVENT_INTERFACE,INSTALL_EXT_MGMT_INTERFACEand INSTALL_EXT_SH_INTERFACE parameters to floating point IPs.
|
|
Step 4
|
Set Management Module details, by setting values of INSTALL_MM_IP,INSTALL_MM_USER and INSTALL_MM_PWD parameters to MM host name or IP address, MM user id and MM password respectively.
|
|
Step 2
|
|
Step 3
|
From the home directory execute following command:exp system/sscsystem@SSC1 FILE=scc_dump.dmp log=scc_export_dump.log STATISTICS=none direct=Y owner=spradm
|
|
Step 4
|
|
Step 6
|
|
Step 7
|
and then execute the following command: select 'DROP SEQUENCE ' || SEQUENCE_NAME || ';' seq from USER_SEQUENCES
|
|
Step 8
|
|
Step 9
|
Ensure that there are no sequences by executing following SQL command: SELECT COUNT(*) FROM USER_SEQUENCES
|
|
Step 10
|
Execute the output of following SQL statement to drop all the object types: SELECT 'DROP TYPE ' || OBJECT_NAME || ' VALIDATE;' A FROM USER_OBJECTS WHERE OBJECT_TYPE = 'TYPE
|
|
Step 11
|
Ensure that there are no object types by executing following SQL command: SELECT COUNT(*) FROM USER_OBJECTS WHERE OBJECT_TYPE = 'TYPE'
|
|
Step 12
|
Execute following SQL statement:SELECT 'ALTER TABLE ' || TABLE_NAME || ' DISABLE CONSTRAINT ' || CONSTRAINT_NAME || ';' A FROM USER_CONSTRAINTS WHERE CONSTRAINT_TYPE = 'R'
|
|
Step 13
|
Ensure that the foreign key constraints are disabled by issuing following SQL statement:SELECT CONSTRAINT_NAME, STATUS FROM USER_CONSTRAINTS WHERE CONSTRAINT_TYPE = 'R'
|
|
Step 14
|
import the data on the host2 that is in the SSC2 application instance by issuing following command: imp system/sscsystem@SSC2 FILE=scc_dump.dmp log=scc_import_dump.log FROMUSER=spradm TOUSER=spradm IGNORE=y STATISTICS=none buffer=99999
|
|
Step 15
|
Login to SSC2 database using sqlplus by issuing the following command: sqlplus spradm/spr_adm@SSC2and then execute following command:SELECT 'ALTER TABLE ' || TABLE_NAME || ' ENABLE CONSTRAINT ' || CONSTRAINT_NAME || ';' A FROM USER_CONSTRAINTS WHERE CONSTRAINT_TYPE = 'R';
|
|
Step 16
|
Execute the following SQL command:SELECT CONSTRAINT_NAME, STATUS FROM USER_CONSTRAINTS WHERE CONSTRAINT_TYPE = 'R';
|
|
Step 17
|
Truncate the session tracker table by issuing following command TRUNCATE TABLE SPR_SESSION_TRACKER
|
|
Step 18
|
Gather SSC2 database statistics by first log-in to the database by issuing following command: sqlplus system/sscsystem@SSC2and then collect the schema statistics by issuing following command:execute dbms_stats.gather_schema_stats('SPRADM',60)
|
|
Step 19
|
|
•
|
Viewing Protection Mode: This query displays the level and mode of data protection as well as database role and switch over status for a primary physical standby or snapshot standby database.
|
|
•
|
Viewing Redo Apply and Transport Status: This query displays redo apply and redo transport status of a physical standby database.
|
|
•
|
Viewing Archive Redo Log Files Information: This query displays information about archived redo log files that have been received by a physical or snapshot standby database from the primary database.
|
|
•
|
Viewing Archived Log History: This query displays the archived log history information.
|
|
•
|
Viewing Data Guard Status Messages: This query displays the messages generated due to data guard events, these messages are stored in alter log or server process trace file
|
|
•
|
Viewing Status of Redo Transport Destination: This query displays the status of each redo transport destination, for the destinations that are standby databases.
|
|
Step 4
|
In ssctemp.properites chose for SAN based installation and HA enabled options.
|
|
Step 5
|
In createGrid.cfg for the stand-by database give the name of blade with disk based SPR.
|
|
Step 6
|
|
Step 2
|
|
Step 3
|
|
Step 4
|
|
Step 2
|
|
Step 4
|
|
Step 5
|
|
Step 4
|
Important: If your SSC cluster deployment is using multiple hosts or blades, then you need to run this un-installation wizard on each such host.|
Step 2
|
Ensure that your X windows application such as xterm or xming is active and running.
|
|
Step 4
|
Execute the script uninstallSSC, by issuing following command
|
|
Step 6
|
Click Next, the un-installer first stops and then removes SSC related database and applications , by executing the clean-up scripts and displaying appropriate messages.
|
|
Step 7
|
Click Done to exit SSC un-installer.
|
|
Step 8
|
You can access detailed log of SSC un-installation process in ../var/log/messagesfile.
|
Important: After executing un-installation wizard, you can ensure that the un-installation was complete, by checking that processes related to database, IMDB and SSC application are not active.